The XCP CAN Definition block defines the CAN settings necessary to manage an XCP connection on CAN.
XCPSlave CAN Definition
Woodward Custom XCPSlave
This block establishes a logical XCP connection on the indicated CAN channel. There can be as many XCP CAN Definition blocks in the application model as is desired.
There can be more than one XCP CAN definition block referencing the same CAN channel, but these blocks will need to be configured with unique CAN identifiers.
The XCP Command packets are responded to in IDLE time of the application, while data acquisition list (DAQ) packets will be transmitted in association
with the event trigger requested by the XCP Master. The configuration of available DAQ event triggers is provided by the Event Definition block.
DAQ lists have a limitation that the number of DAQ lists * the number of ODTs per list must be less than or equal to 252. The number of ODT Entries per ODT is fixed at 7 for CAN.
In order for the Woodward Custom XCP Slave library to be used, the user's MotoHawk security token will need to have the proper license added to it. For instructions on how to accomplish this, please see the instructions for adding the MotoHawk XCPSlave Library license.
A user can check whether their MotoHawk security token has the needed product license at the Matlab command line by executing the woodward_custom_xcpslave_check_license command. A returned value of 1 means the MotoHawk XCPSlave Library is licensed, while a returned value of 0 means it is not.
Parameter Field | Values | Comments/Description |
---|---|---|
XCP Instance Name | String | The unique name assigned to this logical CAN connection. |
CAN Channel Name | String | Specify which CAN channel to use - CAN_1, CAN_2, CAN_3 |
Receive Queue Size | Number | The number of block transfer packets to buffer |
Receive ID (CRO) | Number, 29 or 11 bits | The CAN Identifier used to send messages to this XCP connection. |
Receive ID Type (0=Std, 1=Ext) | Number, 0 or 1 | Specify 0 for Standard (11-bit identifiers), 1 for Extended (29-bit identifiers) on the CAN bus. |
Broadcast Receive ID | Number, 29 or 11 bits | The CAN Identifier used for broadcast messages on this CAN channel. |
Broadcast Receive ID Mask | Number, 29 or 11 bits | A CAN identifier mask, usually hex2dec('1FFFFFFF') |
Receive ID Mask | Number, 29 or 11 bits | A CAN identifier mask, usually hex2dec('1FFFFFFF') |
Transmit ID (DTO/DAQ) | Number, 29 or 11 bits | The CAN Identifier this XCP connection uses to send responses or DAQ. |
Transmit ID Type (0=Std, 1=Ext) | Number, 0 or 1 | Specify 0 for Standard (11-bit identifiers), 1 for Extended (29-bit identifiers) on the CAN bus. |
Total Number of DAQs (1-252) | Number, 1-252 | Set the number of Data Acquisitions (DAQs) for this CAN connection. DAQs are lists of automatically transmitted signals. |
Total Number of Object Descriptors (ODT) per (DAQ) (1-252) | Number, 1-252 | Set the number of Object Descriptors (ODTs) per Data Acquisition list. ODTs determine the length of each DAQ list in CAN messages. |
Copyright 2013 Woodward Inc. All Rights Reserved. | Visit Us: mcs.woodward.com |